home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / newsgroups / misc.20041116-20060924 / 000173_rock_spambust_violin@yahoo.com_Tue Oct 18 09:00:41 2005.msg < prev    next >
Internet Message Format  |  2020-01-01  |  2KB
  1. Path: newsmaster.cc.columbia.edu!panix!newsfeed-00.mathworks.com!newscon06.news.prodigy.com!prodigy.net!border1.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!f14g2000cwb.googlegroups.com!not-for-mail
  2. From: "tomviolin" <rock_spambust_violin@yahoo.com>
  3. Newsgroups: comp.protocols.kermit.misc
  4. Subject: Re: set timeout for HTTP transfers?
  5. Date: 17 Oct 2005 22:18:24 -0700
  6. Organization: http://groups.google.com
  7. Lines: 17
  8. Message-ID: <1129612704.650310.8890@f14g2000cwb.googlegroups.com>
  9. References: <1129528599.691472.17580@g44g2000cwa.googlegroups.com>
  10.    <slrndl7tn1.g88.fdc@sesame.cc.columbia.edu>
  11. NNTP-Posting-Host: 68.166.82.137
  12. Mime-Version: 1.0
  13. Content-Type: text/plain; charset="iso-8859-1"
  14. X-Trace: posting.google.com 1129612709 28248 127.0.0.1 (18 Oct 2005 05:18:29 GMT)
  15. X-Complaints-To: groups-abuse@google.com
  16. NNTP-Posting-Date: Tue, 18 Oct 2005 05:18:29 +0000 (UTC)
  17. User-Agent: G2/0.2
  18. X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7,gzip(gfe),gzip(gfe)
  19. Complaints-To: groups-abuse@google.com
  20. Injection-Info: f14g2000cwb.googlegroups.com; posting-host=68.166.82.137;
  21.    posting-account=ornCOQwAAAAyCG4a7NOAj_SMr54FiqNu
  22. Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15416
  23.  
  24. Thanks for the detailed reply.  What I'll probably do is run another
  25. process in parallel to get the HTTP data and record the result in a
  26. file, and then the Kermit script will just read it from the file.  That
  27. way if the HTTP GET blocks, the other script will simply be collecting
  28. the most recently read data again, which is better than having the
  29. whole script hang.
  30.  
  31. In case anyone is curious, I'm collecting atmospheric CO2 readings
  32. locally and grabbing weather data from another site to store in the
  33. same data record.  If the weather data is delayed slightly it's no big
  34. deal, but the CO2 data, which is the whole point of the study, needs to
  35. be recorded several times a minute without fail.
  36.  
  37. I'm still not quite sure why the HTTP GET is failing, I'm grabbing it
  38. from another server in the same building.  But that's another whole
  39. issue I'll have to resolve later.
  40.